Sunshine

What went brightly and made the team shine?

Our release went out on time with zero critical bugs — huge win for the whole team.
Pairing on the new feature really sped things up and we learned a lot from each other.
Stakeholders gave great feedback on the demo, it felt amazing to be recognised.
Clouds

What felt unclear, uncertain or murky?

I'm still not sure who owns the deployment process now that things have changed.
The requirements for the next epic feel vague and keep shifting.
It's unclear how we're prioritising bug fixes versus new features.
Storms

What was stormy, painful or held us back?

The staging environment kept crashing and cost us hours of debugging time.
Too many last-minute scope changes derailed our sprint plan.
Communication between teams broke down and we duplicated work.
Forecast

What do we predict or want for the road ahead?

If we lock requirements earlier, next sprint should be much smoother.
I predict the new CI pipeline will speed up our releases noticeably.
Let's agree on clear ownership so deployments stop being a guessing game.

What is the Weather Forecast Retrospective

The Weather Forecast Retrospective turns reflection into a visual, intuitive experience by mapping your team's recent journey onto familiar weather patterns. Just as a meteorologist reads the skies, your team uses sunshine, storms, clouds, and forecasts to express how things felt during the last sprint or project phase — making it easy for everyone to share their mood and observations in a relatable, low-pressure way. The format works by inviting participants to reflect across four weather-inspired themes: what's been bright and going well (Sunshine), what's been stormy and challenging (Storms), what's uncertain or unclear (Clouds), and what they predict is coming next (Forecast). This blend of looking back and looking forward helps teams celebrate wins, surface problems, and proactively plan for what's ahead. Because the metaphor is universal and approachable, it lowers the barrier for honest conversation and works especially well for teams who want a fresh, engaging alternative to traditional retrospective formats. Whether you're running an agile sprint retrospective or a broader project review, the Weather Forecast Retro encourages emotional honesty, shared understanding, and forward-thinking action items. It's a creative way to read the team climate, identify the storms before they hit, and steer toward clearer skies — all within TeamRetro's collaborative space.

Weather Forecast retrospective format

Sunshine

What went brightly and made the team shine?

Sunshine represents the highlights — the wins, successes, and positive moments worth celebrating. Encourage the team to be specific and to recognise both individual and collective achievements. Starting with the positives sets an upbeat tone and reminds everyone of the good things, even after a tough sprint.

Clouds

What felt unclear, uncertain or murky?

Clouds capture the grey areas — ambiguity, confusion, and things that aren't quite problems yet but could become them. Use this theme to surface unclear requirements, undefined ownership, or decisions that need more clarity. Naming these early helps prevent them from turning into storms later.

Storms

What was stormy, painful or held us back?

Storms are the challenges, blockers, and frustrations that disrupted the team. Create a safe space for honesty and focus on the issues and systems rather than blaming individuals. These are the items most likely to turn into concrete action points, so dig into root causes where possible.

Forecast

What do we predict or want for the road ahead?

The Forecast looks forward — predictions, hopes, and what the team wants to change next. Encourage participants to think about what would improve the outlook and what early actions could clear the skies. This naturally bridges reflection into actionable next steps and commitments.

When to use this retrospective

  • At the end of a sprint when you want an engaging, visual alternative to a standard 'what went well / what didn't' retrospective.
  • When team morale or mood is a key factor and you want to surface how people are feeling alongside the facts.
  • For project milestones or quarterly reviews where looking back and forecasting ahead are both valuable.
  • When a team feels fatigued by repetitive retrospective formats and needs a fresh, playful way to reflect.
  • After a turbulent period to safely name the storms, clear the clouds, and rebuild a positive outlook.

Suggested icebreaker questions

  • If your week was a type of weather, what would the forecast say?
  • What's your favourite kind of weather and does it match your current mood at work?

Ideas and tips for your retrospective meeting

  • Start with Sunshine to build a positive atmosphere before diving into the tougher Storms and Clouds.
  • Lean into the weather metaphor to keep things light, but make sure conversations still land on concrete, actionable outcomes.
  • Encourage everyone to contribute to each theme so the forecast reflects the whole team, not just the loudest voices.
  • Frame Storms around processes and systems rather than individuals to avoid blame and keep the discussion psychologically safe.
  • Use the Forecast theme to convert reflections into clear action items with owners before closing the session.
  • Timebox each theme so you cover the full forecast and leave room to agree on next steps.

Frequently asked questions

What is the Weather Forecast Retrospective?
It's a retrospective format that uses weather metaphors — Sunshine, Clouds, Storms, and Forecast — to help teams reflect on what went well, what was unclear, what was challenging, and what's coming next. The familiar imagery makes it easy and approachable for everyone to share honestly.
How long does a Weather Forecast Retrospective take?
A typical session runs 45 to 60 minutes for a team of five to eight people. Allow more time if you have a larger group or want to dive deeply into action planning under the Forecast theme.
When should I use this retrospective instead of a standard one?
Use it when you want a fresh, engaging alternative to repetitive formats, when team mood and morale are important, or after a turbulent period when you want to safely surface challenges and rebuild a positive outlook.
How is it different from the Mad Sad Glad retrospective?
Mad Sad Glad focuses purely on emotions from the past period, while the Weather Forecast Retro blends mood with looking forward through its Forecast theme, encouraging teams to predict and plan for what's ahead.
Can remote and distributed teams run this retrospective?
Yes. In TeamRetro everyone can add ideas to each weather theme in real time or asynchronously, then group, vote, and discuss together — making it ideal for remote and hybrid teams.
How do I turn the discussion into action items?
Use the Forecast theme to capture predictions and desired changes, then convert the top-voted items into clear action points with owners and due dates before closing the session.

New to retrospectives? Read our guide on how to run a retrospective →